<!DOCTYPE html>
<html>
<head>
    <meta http-equiv="content-type" content="text/html; charset=utf-8"/>
    <title></title>
    <link rel="Stylesheet" href="css/analysis.css" />
    <script type="text/javascript">
        function init() {
            if (window.location.hash) {
                var parentDiv, nodes, i, helpInfo, helpId, helpInfoArr, helpEnvFilter, envContent, hideEnvClass, hideNodes;
                helpInfo = window.location.hash.substring(1);
                    if(helpInfo.indexOf("-")) {
                        helpInfoArr = helpInfo.split("-");
                        helpId = helpInfoArr[0];
                        helpEnvFilter = helpInfoArr[1];
                    }
                    else {
                        helpId = helpInfo;
                    }
                parentDiv = document.getElementById("topics");
                nodes = parentDiv.children;
                    hideEnvClass = (helpEnvFilter === "OnlineOnly"? "PortalOnly": "OnlineOnly");
                    if(document.getElementsByClassName) {
                        hideNodes = document.getElementsByClassName(hideEnvClass);
                    }
                    else {
                        hideNodes = document.querySelectorAll(hideEnvClass);
                    }
                for(i=0; i < nodes.length; i++) {
                    if(nodes[i].id !== helpId) {
                        nodes[i].style.display ="none";
                    }
                    }
                    for(i=0; i < hideNodes.length; i++) {
                        hideNodes[i].style.display ="none";
                    }
                }
            }
    </script>
</head>
<body onload="init()">
<div id="topics">
    <div id="toolDescription" class="largesize">
        <h2>Connect Origins to Destinations</h2><p/>
        <h2><img src="./images/GUID-7266D30B-0250-4132-B1A5-9B59F0212FAD-web.png" alt="Connect Origins to Destinations"></h2>
        <hr/>
    <p>Connect Origins to Destinations measures the travel time or distance between pairs of points. The tool can report straight-line distances; distances based on a travel mode, such as walking or driving; or trip durations based on a travel mode. Using this tool, you can do the following:
    </p>
    <p>
        <ul>
            <li>Calculate the total distance or time commuters travel on their  home-to-work trips.
            </li>
            <li>Measure how far customers are traveling to shop at your stores. Use this information to define your market reach, especially when targeting advertising campaigns or choosing new store locations.
            </li>
            <li>Calculate the expected trip mileage for your fleet of vehicles. Afterward, run the Summarize Within tool to report mileage by state or other region.
            </li>
        </ul>
        
    </p>
    <p>You provide starting and ending points, and the tool returns a layer containing route lines, including measurements, between the paired origins and destinations. 
    </p>
    <p>If  <b>Use current map extent</b> is checked, only the features that are visible within the current map extent will be considered in the analysis.  If unchecked, all features in the input layer will be considered, even if they are outside the current map extent.
    </p>
    </div>
    <!--Parameter divs for each param-->
    <div id="originsLayer">
        <div><h2>Choose point layer representing the origin locations</h2></div>
        <hr/>
        <div>
            <p>Choose the point layer representing the origin or origins.  
The tool supports up to  5,000 origins and  5,000 destinations. </p>
            <p>If you choose a layer that has exactly one origin, it will connect to all destinations.
            </p>
            <p>In addition to choosing a layer from your map, you can select  <b>Choose Analysis Layer</b> found at the bottom of the drop-down list. This option opens a gallery where you can browse to and select datasets from various sources to use in your analysis. 
            </p>
        </div>
    </div>
    <div id="destinationsLayer">
        <div><h2>Choose the destinations layer</h2></div>
        <hr/>
        <div>
            <p>Choose the layer 
representing the destination or destinations to which the origins should connect. The tool supports up to  5,000 origins and  5,000 destinations. </p>
            <p>If you choose a layer that has exactly one destination, all the origins will connect to that destination. 
            </p>
            <p>If there is one origin and many destinations, the tool connects the origin to each of the destinations.
            </p>
            <p>In addition to choosing a layer from your map, you can select  <b>Choose Analysis Layer</b> found at the bottom of the drop-down list. This option opens a gallery where you can browse to and select datasets from various sources to use in your analysis. 
            </p>
            <p> If there are many origins and many destinations, you need to have two fields that describe the origin-destination pairs: <b>ID field in origins</b> and <b>Matching ID field in destinations</b>. The tool connects the origin-destination pairs during the analysis. For instance, imagine you have two origins with ID field values of <code>Rosie</code> and <code>Harold</code> and two destinations with the same ID values. The <code>Rosie</code> origin will connect to the <code>Rosie</code> destination, and <code>Harold</code> will connect to <code>Harold</code>. No other connections or measurements are made.
            </p>
            <p>If there are equal numbers of origins and destinations, the ID values must be unique within each layer; for instance, the destinations layer cannot have two  <code>Rosie</code> values. The values in the origin and destination layers must match exactly to make pairs; <code>Harold</code> won't connect to the misspelled value, <code>Harodl</code>. 
            </p>
            <p>The tool also supports connecting each origin to more than one destination or each destination to more than one origin. In such cases, you still need to have two fields that describe the origin-destination pairs. However, only one of the layers (either the origin or the destination layer) needs to have unique ID values.
            </p>
        </div>
    </div>
    <div id="measurementType">
        <div><h2>Measure</h2></div>
        <hr/>
        <div>
            
            <p>Choose whether to connect origins to destinations using straight-line distance or a travel mode. The output routes will  follow roads or walkways and honor applicable rules, such as one-way streets and illegal turns for driving or trucking.  The available travel modes are determined by the administrator of your organization.  
            </p>
            <p>When you choose  <b>Driving Time</b>, <b>Rural Driving Time</b>, or <b>Trucking Time</b> you have options on how to measure the drive time.
                <ul>
                    <li>
                        <p>Uncheck  <b>Use Traffic</b> to find the quickest routes based on fixed speeds.
                        </p>
                        <p>This is the option to choose if you want a general drive-time measurement, not one that is calculated using changing traffic conditions for a specific departure time.
                        </p>
                    </li>
                    <li>
                        <p>Check  <b>Use Traffic</b> to find the quickest routes based on a given start time and changing traffic conditions. By also choosing the <b>Live traffic</b> option, the departure time from the origins is set to the current time, and current and predicted traffic speeds are referenced from sensors and feeds to create the routes. The predicted traffic speeds are calculated by referencing live traffic speeds, historical speeds, and current events such as weather. Traffic speeds are predicted 4 hours into the future, so you can move the slider to set the departure time ahead by up to  4 hours. </p>
                        <p>Use these live-traffic settings to find the drive times for  departing now, departing in one hour from now, and so on.
                        </p>
                    </li>
                    <li>
                        <p>By checking  <b>Use Traffic</b> and choosing <b>Traffic based on typical conditions for</b> a day and time, the tool finds the quickest routes based on historical speed averages for every five-minute  interval across a routine week. The results include traffic but remove the influence of current traffic conditions and events, which may vary significantly from the norm.
                        </p>
                        <p>You can use these historical traffic settings to ask, for instance, &quot;How long would it generally take to reach these destinations when departing at 11:30 a.m. on a Wednesday?&quot;
                        </p>
                        <p>The time you set refers to the time zone in which your origins are located. So if you set the time to 8:00 a.m. and have two origins, one in New York City and another in Los Angeles, the routes will be generated for a departure time of 8:00 a.m. Eastern Time and 8:00 a.m. Pacific Time, respectively.
                        </p>
                    </li>
                </ul>
                
            </p>
            <p>Note that as a vehicle drives away from the origin, time elapses and traffic conditions change. The Connect Origins to Destinations tool accounts for these variations when you check  <b>Use traffic</b>; however, not all regions support traffic. Click the <b>See availability</b> link on the tool to find out whether it is offered in  your study area.
            </p>
            <p> <b>Trucking Time</b> can use dynamic travel speeds based on traffic but only up to the legal truck speed limit. For example, if the dynamic speed for a street based on live traffic is 65 miles per hour but the truck speed limit for that street is 55 miles per hour, the calculation will use 55 miles per hour for that street.
            </p>
        </div>
    </div>
    <div id="barrier_layers">
        <div><h2>Select barrier layers</h2></div>
        <hr/>
        <div>
            <p> One or more features that act as temporary restrictions (barriers) when traveling on the underlying streets. You can specify the barriers using point, line, or polygon features.
            </p>
            <p>  <b>Select barrier layers</b> is available when a travel mode is used as the <b>Measure</b>. If <b>Line distance</b> is used, <b>Select barrier layers</b> will be disabled.
            </p>
            <p>A point barrier can model a fallen tree, an accident, a downed electrical line, or anything that completely blocks traffic at a specific position along the street. Travel is permitted on the street but not through the barrier. You can specify up to 250 features to act as point barriers.
            </p>
            <p>A line barrier prohibits travel anywhere the barrier intersects the streets. For example, a parade or protest that blocks traffic across several street segments can be modeled with a line barrier. If the number of street features intersected by all the line barriers exceeds 500, the tool returns an error.
            </p>
            <p>A polygon barrier prohibits travel anywhere the polygon intersects the streets. One use of this type of barrier is to model floods covering areas of the street network and making road travel there impossible. If the number of street features intersected by all the polygon barriers exceeds 2000, the tool returns an error.
            </p>
        </div>
    </div>
    <div id="routeShape">
        <div><h2>Route shape</h2></div>
        <hr/>
        <div>
            <p>Choose the shape of the route that connects each origin to it's destination:
            </p>
            <ul>
                <li> <b>Straight line</b> - The shape is a straight line connecting the origin-destination pair. This option is best when you want to generate spider diagrams or desire lines (for example, to show which stores customers are visiting).
                </li>
                <li> <b>Follow streets</b> - The shape is based on the underlying street network. This option is best when you want to generate the routes between origins and destinations. <b>Follow streets</b> is disabled when the measure is <b>Line distance</b>.
                </li>
            </ul>
            
            <p>The best route between an origin and it's matched destination is always calculated based on the travel mode, regardless of which route shape is chosen.
            </p>
        </div>
    </div>
    <div id="outputLayer">
        <div><h2>Result layer name</h2></div>
        <hr/>
        <div>
            <p>The name of the feature layer that will be created in  <b>My Content</b> and added to the map. If the feature layer already exists, you will be asked to provide another name. The feature layer will contain a layer for each of the following: routes, unassigned origins, and unassigned destinations when some origins cannot be connected to their destinations.
            </p>
            <p>If you select  <b>Include route layers</b>, each route from the result is also saved as a route layer. A route layer includes all the information for a particular route, such as the stops assigned to the route as well as the travel directions. Creating  route layers is useful if you want to share the individual routes with other members in your organization or to further modify the routes using the <b>Directions</b> button in the map viewer. The route layers use the name provided for the feature layer  as a prefix and the route name generated as part of the analysis, which is added to create a unique name for each route layer.
            </p>
            <p>The maximum number of route layers that can be created is  1,000. If the result contains more than  1,000 routes and  <b>Include route layers</b> is checked, the tool will only create the output feature service.
            </p>
            <p>Using the  <b>Save result in</b> drop-down menu, you can specify the name of a folder in <b>My Content</b> where the feature layer and the route layers, if created, will be saved.
            </p>
        </div>
    </div>
</div>
</html>
